Multi-video capture system

ABSTRACT

Systems and methods provide for capturing, at a first computing device associated with a first user, a first video stream, and presenting, by the first computing device, and indication that a second computing device associated with a second user is located within a predetermined distance of the first computing device. The systems and methods further providing for receiving, by the first computing device, a request to access a second video stream being captured on the second computing device and displaying, by the first computing device, the second video stream being captured on the second computing device, on a display of the first computing device.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.16/178,301, filed on Nov. 1, 2018, which claims the benefit of priorityto U.S. Provisional Application Ser. No. 62/581,439, filed on Nov. 3,2017, each of which are hereby incorporated by reference herein in theirentireties.

BACKGROUND

A messaging system may receive millions of messages from users desiringto share media content such as audio, images, and video between userdevices (e.g., mobile devices, personal computers, etc.). The mediacontent of these messages may be associated with a common geolocation, acommon time period, a common event, and so forth.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and should not be considered aslimiting its scope.

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network,according to some example embodiments.

FIG. 2 is block diagram illustrating further details regarding amessaging system, according to some example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored inthe database of the messaging server system, according to some exampleembodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 5 is a schematic diagram illustrating an example access-limitingprocess, in terms of which access to content (e.g., an ephemeralmessage, and associated multimedia payload of data) or a contentcollection (e.g., an ephemeral message story) may be time-limited (e.g.,made ephemeral), according to some example embodiments.

FIG. 6 is a flowchart illustrating aspects of a method, according tosome example embodiments.

FIGS. 7-10 each show an example user interface of a computing device,according to some example embodiments.

FIG. 11 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 12 illustrates a diagrammatic representation of a machine, in theform of a computer system, within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

Systems and methods described herein relate to sharing media contentitems between devices (e.g., directly or via a messaging system). Forexample, a first user may be recording a video on a first device. Asecond user known to the first user (e.g., a friend, family member,colleague, acquaintance, member of the first user's social network,etc.) may be also capturing video on a second device in a location nearthe first user. Currently, there is no way to know that the second useris capturing video nearby or to view video the second user is currentlycapturing. In example embodiments, the first user may receive anindication on his device that the second user is nearby. The first usermay request to view what the second user is capturing. The first devicemay display what the second user is capturing on a display on the firstdevice. The display may show both video capture streams, the video thefirst user is capturing and the video the second user is capturing. Inone example, the display may show a split screen with both videos. Thefirst user may then indicate that he wishes to send a message with bothvideos to one or more other users. The first device may generate amessage comprising both videos and send it to one or more other users orinclude it in one or more media collections. The one or more other usersmay receive the message comprising both videos and view the message withboth videos on a display of a device. For example, the user receivingthe message may view the message with the videos in split screen format.

Accordingly, example embodiments provide for collaborative video captureand a unique way of displaying multi-video capture and interacting withother users. Moreover, example embodiments allow for capture of videofrom different perspectives based on locations and angles of differentdevices. Furthermore, example embodiments allow for generating messageswith combined videos from different devices/users and viewing combinedvideos from different devices/users.

FIG. 1 is a block diagram illustrating a networked system 100 (e.g., amessaging system) for exchanging data (e.g., messages and associatedcontent) over a network. The networked system 100 includes multipleclient devices 102, each of which hosts a number of client applications104. Each client application 104 is communicatively coupled to otherinstances of the client application 104 and a server system 108 via anetwork 106.

The client device 102 may also be referred to herein as a user device ora user computing device. The client device 102 may comprise, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistant (PDA), smart phone, tablet, ultra-book, netbook, laptop,multi-processor system, microprocessor-based or programmable consumerelectronic, game console, set-top box, computer in a vehicle, or anyother communication device that a user may utilize to access thenetworked system 100. In some embodiments, the client device 102 maycomprise a display module (not shown) to display information (e.g., inthe form of user interfaces). In further embodiments, the client device102 may comprise one or more of touch screens, accelerometers,gyroscopes, cameras, microphones, global positioning system (GPS)devices, and so forth. The client device 102 may be a device of a userthat is used to create media content items such as video, images (e.g.,photographs), audio, and send and receive messages containing such mediacontent items to and from other users. Elements of such media contentfrom multiple messages may then be displayed together as detailedfurther in the example embodiments described below. For example, theclient device 102 may be a first device and may display a first videostream being captured on the first client device 102, and a second videostream that is being captured on a second client device 102. Forexample, the first client device 102 may display both the first videostream being captured by the first client device 102 and the secondvideo stream being captured by the second client device 102, on adisplay screen of the first client device 102 (e.g., as a split screenor other means).

One or more users may interact with the client device 102 (e.g., aperson, a machine, or other means of interacting with the client device102). In example embodiments, the user may not be part of the system100, but may interact with the system 100 via the client device 102 orother means. For instance, the user may provide input (e.g., touchscreen input or alphanumeric input) to the client device 102 and theinput may be communicated to other entities in the system 100 (e.g.,server system 108, etc.) via the network 106. In this instance, theother entities in the system 100, in response to receiving the inputfrom the user, may communicate information to the client device 102 viathe network 106 to be presented to the user. In this way, the user mayinteract with the various entities in the system 100 using the clientdevice 102.

The system 100 may further include a network 106. One or more portionsof network 106 may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), a portion of the Internet, a portion ofthe public switched telephone network (PSTN), a cellular telephonenetwork, a wireless network, a WiFi network, a WiMax network, anothertype of network, or a combination of two or more such networks.

The client device 102 may access the various data and applicationsprovided by other entities in the system 100 via a web client (e.g., abrowser, such as the Internet Explorer® browser developed by Microsoft®Corporation of Redmond, Wash.) or one or more client applications 104.As described above, the client device 102 may include one or more clientapplications 104 (also referred to as “apps”) such as, but not limitedto, a web browser, messaging application, electronic mail (email)application, an e-commerce site application, a mapping or locationapplication, media content editing application, media content viewingapplication, and the like.

In one example, a client application 104 may be a messaging applicationthat allows a user to take a photograph or video, add a caption, orotherwise edit the photograph or video, and then send the photograph orvideo to another user. The message may be ephemeral and be removed froma receiving user device after viewing or after a predetermined amount oftime (e.g., 10 seconds, 24 hours, etc.). An ephemeral message refers toa message that is accessible for a time-limited duration. An ephemeralmessage may be a text, an image, a video and other such content that maybe stitched together in accordance with embodiments described herein.The access time for the ephemeral message may be set by the messagesender. Alternatively, the access time may be a default setting or asetting specified by the recipient. Regardless of the setting technique,the message is transitory.

The messaging application may further allow a user to create a galleryor media collection. A gallery may be a collection of photos and videoswhich may be viewed by other users “following” the user's gallery (e.g.,subscribed to view and receive updates in the user's gallery). Thegallery may also be ephemeral (e.g., lasting 24 hours, lasting aduration of an event (e.g., during a music concert, sporting event,etc.), or other predetermined time).

An ephemeral message may be associated with a message durationparameter, the value of which determines an amount of time that theephemeral message will be displayed to a receiving user of the ephemeralmessage by the client application 104. The ephemeral message may befurther associated with a message receiver identifier and a messagetimer. The message timer may be responsible for determining the amountof time the ephemeral message is shown to a particular receiving useridentified by the message receiver identifier. For example, theephemeral message may only be shown to the relevant receiving user for atime period determined by the value of the message duration parameter.

In another example, the messaging application may allow a user to storephotographs and videos and create a gallery that is not ephemeral andthat can be sent to other users. For example, to assemble photographsand videos from a recent vacation to share with friends and family.

In some embodiments, the one or more client applications 104 may beincluded in a given one of the client device 102, and configured tolocally provide the user interface and at least some of thefunctionalities with the application 104 configured to communicate withother entities in the system 100 (e.g., server system 108), on an asneeded basis, for data and/or processing capabilities not locallyavailable (e.g., access location information, to authenticate a user, toverify a method of payment, access media content stored on a server,sync media content between the client device 102 and a server computer,etc.). Conversely, one or more applications 104 may not be included inthe client device 102, and then the client device 102 may use its webbrowser to access the one or more applications hosted on other entitiesin the system 100 (e.g., server system 108).

A server system 108 may provide server-side functionality via thenetwork 106 (e.g., the Internet or wide area network (WAN)) to one ormore client devices 102. The server system 108 may include anapplication programming interface (API) server 110, an applicationserver 112, a messaging server application 114, and a media contentprocessing server 116, a social network system 122, and a multi-videocapture system 124, which may each be communicatively coupled with eachother and with one or more data storage(s), such as database(s) 120.

The server system 108 may be a cloud computing environment, according tosome example embodiments. The server system 108, and any serversassociated with the server system 108, may be associated with acloud-based application, in one example embodiment. The one or moredatabase(s) 120 may be storage devices that store information such asuntreated media content, original media content from users (e.g., highquality media content), processed media content (e.g., media contentthat is formatted for sharing with client devices 102 and viewing onclient devices 102), stitched audio data streams, user information, userdevice information, and so forth. The one or more database(s) 120 mayinclude cloud-based storage external to the server system 108 (e.g.,hosted by one or more third party entities external to the server system108). While the storage devices are shown as database(s) 120, it isunderstood that the system 100 may access and store data in storagedevices such as databases 120, blob storages, and other type of storagemethods.

Accordingly, each client application 104 is able to communicate andexchange data with another client applications 104 and with the serversystem 108 via the network 106. The data exchanged between clientapplications 104, and between a client application 104 and the serversystem 108, includes functions (e.g., commands to invoke functions) aswell as payload data (e.g., text, audio, video or other multimediadata).

The server system 108 provides server-side functionality via the network106 to a particular client application 104. While certain functions ofthe system 100 are described herein as being performed by either aclient application 104 or by the server system 108, it will beappreciated that the location of certain functionality either within theclient application 104 or the server system 108 is a design choice. Forexample, it may be technically preferable to initially deploy certaintechnology and functionality within the server system 108, but to latermigrate this technology and functionality to the client application 104where a client device 102 has a sufficient processing capacity.

The server system 108 supports various services and operations that areprovided to the client application 104. Such operations includetransmitting data to, receiving data from, and processing data generatedby the client application 104. This data may include message content,client device information, geolocation information, media annotation andoverlays, message content persistence conditions, social networkinformation, and live event information, date and time stamps, asexamples. Data exchanges within the networked system 100 are invoked andcontrolled through functions available via user interfaces (UIs) of theclient application 104.

In the server system 108, an application program interface (API) server110 is coupled to, and provides a programmatic interface to, anapplication server 112. The application server 112 is communicativelycoupled to a database server 118, which facilitates access to a database120 in which is stored data associated with messages processed by theapplication server 112.

The API server 110 server receives and transmits message data (e.g.,commands and message payloads) between the client device 102 and theapplication server 112. Specifically, the API server 110 provides a setof interfaces (e.g., routines and protocols) that can be called orqueried by the client application 104 in order to invoke functionalityof the application server 112. The API server 110 exposes variousfunctions supported by the application server 112, including accountregistration, login functionality, the sending of messages, via theapplication server 112, from a particular client application 104 toanother client application 104, the sending of media files (e.g., imagesor video) from a client application 104 to the messaging applicationserver 114, and for possible access by another client application 104,the setting of a collection of media data (e.g., Story, gallery, mediacollection), the retrieval of a list of friends of a user of a clientdevice 102, the retrieval of such collections, the retrieval of messagesand content, the adding and deletion of friends to a social graph, thelocation of friends within a social graph, opening and application event(e.g., relating to the client application 104), detection andnotification of user devices nearby a particular user device, and soforth.

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, a mediacontent processing system 116, a social network system 122, and amulti-video capture system 124. The messaging server application 114implements a number of message processing technologies and functions,particularly related to the aggregation and other processing of content(e.g., textual and multimedia content) included in messages receivedfrom multiple instances of the messaging client application 104. As willbe described in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories, galleries, or media collections). These collections are thenmade available, by the messaging server application 114, to the clientapplication 104. Other processor and memory intensive processing of datamay also be performed server-side by the messaging server application114, in view of the hardware requirements for such processing.

The application server 112 also includes media content processing system116 that is dedicated to performing various media content processingoperations, typically with respect to images or video received withinthe payload of a message at the messaging server application 114. Themedia content processing system 116 may access one or more data storages(e.g., database(s) 120) to retrieve stored data to use in processingmedia content and to store results of processed media content.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 within thedatabase 120. Examples of functions and services supported by the socialnetwork system 122 include the identification of other users of thenetworked system 100 with which a particular user has relationships oris “following,” and also the identification of other entities andinterests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to one or more database(s) 120 inwhich is stored data associated with messages processed by the messagingserver application 114.

The messaging server application 114 may be responsible for generationand delivery of messages between users of client devices 102. Themessaging application server 114 may utilize any one of a number ofmessage delivery networks and platforms to deliver messages to users.For example, the messaging application server 114 may deliver messagesusing electronic mail (e-mail), instant message (IM), Short MessageService (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP))messages via wired (e.g., the Internet), plain old telephone service(POTS), or wireless networks (e.g., mobile, cellular, WiFi, Long TermEvolution (LTE), Bluetooth).

The multi-video system 124 may be responsible for detecting user devicesnearby a particular user device, notification of the detected nearbydevice(s), generating a message comprising video received from aplurality of user computing devices (e.g., client devices 102), and soforth, as described in further detail below.

FIG. 2 is block diagram illustrating further details regarding thesystem 100, according to example embodiments. Specifically, the system100 is shown to comprise the messaging client application 104 and theapplication server 112, which in turn embody a number of somesubsystems, namely an ephemeral timer system 202, a collectionmanagement system 204, and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a story, gallery, media collection, etc.),selectively display and enable access to messages and associated contentvia the messaging client application 104. Further details regarding theoperation of the ephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery,” an “event story” or, a “media collection.” Such a collectionmay be made available for a specified time period, such as the durationof an event to which the content relates. For example, content relatingto a music concert may be made available as a “Story” for the durationof that music concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation (e.g. money, non-money credits or pointsassociated with the communication system or a third party reward system,travel miles, access to artwork or specialized lenses, etcetera) may bepaid to a user for inclusion of user generated content into acollection. In such cases, the curation interface 208 operates toautomatically make payments to such users for the use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the networked system 100. The annotation system 206operatively supplies a media overlay (e.g., a filter) to the messagingclient application 104 based on a geolocation of the client device 102.In another example, the annotation system 206 operatively supplies amedia overlay to the messaging client application 104 based on otherinformation, such as, social network information of the user of theclient device 102. A media overlay may include audio and visual contentand visual effects. Examples of audio and visual content includepictures, texts, logos, animations, and sound effects. An example of avisual effect includes color overlaying. The audio and visual content orthe visual effects can be applied to a media content item (e.g., aphoto) at the client device 102. For example, the media overlayincluding text that can be overlaid on top of a photograph generatedtaken by the client device 102. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice beach), aname of a live event, or a name of a merchant overlay (e.g., BeachCoffee House). In another example, the annotation system 206 uses thegeolocation of the client device 102 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 120 andaccessed through the database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay is to be offered to other users. The annotationsystem 206 generates a media overlay that includes the uploaded contentand associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time

FIG. 3 is a schematic diagram 300 illustrating data which may be storedin the database 120 of the server system 108, according to certainexample embodiments. While the content of the database 120 is shown tocomprise a number of tables, it will be appreciated that the data couldbe stored in other types of data structures (e.g., as an object-orienteddatabase).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events etc. Regardless of type, any, entity regarding which theserver system 108 stores data may be a recognized entity. Each entity isprovided with a unique identifier, as well as an entity type identifier(not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of varioustypes, including a user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filers includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filer is a data filer, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102 or thecurrent time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video or audio data, which are compiled into acollection a story, gallery, or media collection). The creation of aparticular collection may be initiated by a particular user (e.g., eachuser for which a record is maintained in the entity table 302). A usermay create a “personal story” in the form of a collection of contentthat has been created and sent/broadcast by that user. To this end, theuser interface of the messaging client application 104 may include anicon that is user selectable to enable a sending user to add specificcontent, to his or her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automaticallyor using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users, whose client devices 102 havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some in some embodiments, generated by a client application104 for communication to a further client application 104 or themessaging server application 114. The content of a particular message400 is used to populate the message table 314 stored within the database120, accessible by the messaging server application 114. Similarly, thecontent of a message 400 is stored in memory as “in-transit” or“in-flight” data of the client device 102 or the application server 112.The message 400 is shown to include the following components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102, and that is included in the message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from the memory component of the client        device 102, and that is included in the message 400.    -   A message annotations 412: annotation data (e.g., filters,        stickers or other enhancements) that represents annotations to        be applied to message image payload 406, message video payload        408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message 400        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message 400. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address or device identifier)        indicative of a user of the client device 102 on which the        message 400 was generated and from which the message 400 was        sent    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address or device identifier)        indicative of a user of the client device 102 to which the        message 400 is addressed.

The contents (e.g. values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message story 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the client application 104. In oneembodiment, an ephemeral message 502 is viewable by a receiving user forup to a maximum of 10 seconds, depending on the amount of time that thesending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message story 504 (e.g., a personal story, or an event story).The ephemeral message story 504 has an associated story durationparameter 508, a value of which determines a time-duration for which theephemeral message story 504 is presented and accessible to users of thenetworked system 100. The story duration parameter 508, for example, maybe the duration of a music concert, where the ephemeral message story504 is a collection of content pertaining to that concert.Alternatively, a user (either the owning user or a curator user) mayspecify the value for the story duration parameter 508 when performingthe setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral messagestory 504 has an associated story participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message story504. Accordingly, a particular ephemeral message story 504 may “expire”and become inaccessible within the context of the ephemeral messagestory 504, prior to the ephemeral message story 504 itself expiring interms of the story duration parameter 508. The story duration parameter508, story participation parameter 510, and message receiver identifier424 each provide input to a story timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message story 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message story 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the story timer 514 operationally controls the overalllifespan of an associated ephemeral message story 504, as well as anindividual ephemeral message 502 included in the ephemeral message story504. In one embodiment, each and every ephemeral message 502 within theephemeral message story 504 remains viewable and accessible for atime-period specified by the story duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message story 504, based on a story participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message story 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message story 504based on a determination that it has exceeded an associated storyparticipation parameter 510. For example, when a sending user hasestablished a story participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message story 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message story 504 either when the storyparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message story 504 has expired, or when theephemeral message story 504 itself has expired in terms of the storyduration parameter 508.

In certain use cases, a creator of a particular ephemeral message story504 may specify an indefinite story duration parameter 508. In thiscase, the expiration of the story participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message story504 will determine when the ephemeral message story 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage story 504, with a new story participation parameter 510,effectively extends the life of an ephemeral message story 504 to equalthe value of the story participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message story 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the system 100 (and,for example, specifically the messaging client application 104 to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage story 504 to no longer be displayed within a user interface ofthe client application 104. Similarly, when the ephemeral timer system202 determines that the message duration parameter 506 for a particularephemeral message 502 has expired, the ephemeral timer system 202 causesthe client application 104 to no longer display an indicium (e.g., anicon or textual identification) associated with the ephemeral message502.

FIG. 6 is a flow chart illustrating aspects of a method 600, accordingto some example embodiments. In operation 602, a computing device (e.g.,client device 102) captures a first video stream. For example, thecomputing device may be a first computing device associated with a firstuser. The first user may interact with a display or user interface onthe first computing device to indicate a desire to capture a photographor video. For example, the first user may press and hold on the displayto capture video. The first computing device may detect the userinteraction and start capturing a video stream via a camera device ofthe first computing device.

In operation 604, the first computing device presents an indication thata second computing device is nearby (e.g., within a predetermineddistance from the first computing device). For example, the firstcomputing device may detect when computing devices associated with otherusers (e.g., friends, family members, colleagues, acquaintances, membersof the first user's social network, etc.) are nearby, such as within apredetermined distance from the first computing device (e.g., within afew feet, at a similar geolocation, within a half mile, within 5 miles,etc.). The first computing device may be able to detect the othercomputing device directly or may receive a notification from a servercomputing system (e.g., server system 108) that one or more othercomputing devices associated with the first user are within apredetermined distance.

In one example, the first computing device sends location dataassociated with the first computing device to a server system (e.g.,server system 108, multi-video capture system 124, etc.). For example,the first computing device may comprise global positioning system (GPS)or other technology used to generate location data (e.g., coordinates,an address, a business or other location, etc.). The first computingdevice may send the location data periodically to the server system orspecifically in a request for whether there are any nearby devicesassociated with users in the user's social network.

The server system receives the location data associated with the firstcomputing device and uses the location data to determine a location ofthe first computing device and whether there are any other computingdevices nearby (e.g., within a predetermined distance from the firstcomputing device, as explained above) the location of the firstcomputing device, based on location data the server system is receivingor has received from other computing devices associated with otherusers. The server system may determine whether any of users associatedwith the computing devices that are nearby the first computing deviceare within a social network of the user associated with the firstcomputing device. For example, the server system may access a datasource (e.g., social graph or entity graph 304) to determine if any ofthe users associated with the nearby computing devices are within theuser's social network. If the server system determines that there areone or more devices nearby that are associated with users in the user'ssocial network, it returns to the first computing device, dataassociated with the one or more devices and/or associated users. In oneexample, the server system may return information for only the nearestdevice/user or the device associated with the user that has the closestrelationship to the user according to a social or entity graph or othermeans. The first computing device receives the information or dataassociated with the one or more devices and/or associated users.

The first computing device may present the indication that the secondcomputing device is nearby, by providing a message or icon on thedisplay of the first computing device. FIG. 7 shows an example userdevice 702 with a display 706 that shows a first video stream 708 beingcaptured by the first computing device. FIG. 7 also shows an example ofhow an indication may be displayed to a user on the display 706. Theindication may be an icon 704 that tells the user that a friend (orother user in the user's social network) is nearby. In this example, theicon 706 indicates that a friend is nearby. In other examples, the icon706 could indicate that more than one friend is nearby.

The first computing device may receive a selection to view a list of theone or more users that are nearby and display a list of users nearby. Inone example, the list includes only one user. In another example thelist includes a plurality of nearby users. For example, the user mayselect the icon 704 and upon detection of the selection the computingdevice may display the user or users nearby. Each of the users in thelist may also be selectable to display further information about eachuser, to send a message to the user, to display an option to view and/orcapture video that the other user is currently capturing, and so forth.

Returning to FIG. 6, in operation 606, the first computing devicereceives a request to access a second video stream being captured on thesecond computing device. For example, the first user may interact withthe first computing device display or via buttons or other means torequest access to the second video stream being captured on his friend'scomputing device. In one example, the first user may press or otherwiseinteraction with the icon 704 shown in FIG. 7 to request access to thesecond video stream. FIG. 8 shows an example second computing device 802with a display 806 showing a second video stream 808 being captured bythe second computing device associated with a second user.

In one example, the first computing device sends a message to the secondcomputing device requesting access to the video being captured by thesecond computing device. In one example, the second computing devicedetermines whether or not the first computing device is authorized toaccess the video being captured by the second computing device. Forexample, the second computing device determines whether the first userassociated with the first computing device is within the second user'ssocial network, may display a message to the second asking the seconduser whether or not the second user would like to grant access of thevideo being captured to the first user, or the like. Once the secondcomputing device determines that the first computing device isauthorized to access the video being captured by the second computingdevice, the second computing device may send the video stream beingcaptured to the first computing device.

The video stream may be sent from the second computing device andreceived by the first computing device via any video streamingtechnology. For example, a WIFI direct connection may be establishedbetween the first computing device and the second computing device andthe video may be streamed via the WIFI direction connection. In anotherexample, the video may be streamed via a backend server system (e.g.,server system 108). For example, the second computing device may sendthe video stream to the backend server and the backend server may sendthe video stream to the first computing device. Other forms of videostreaming and connections may be used in other embodiments.

In operation 608 of FIG. 6, the first computing device displays thesecond video stream being captured on the second computing device on thedisplay of the first computing device (e.g., in response to the requestto access the second video stream). In one example, the first computingdevice may display both the first video stream being captured by thefirst computing device, and the second video stream being captured bythe second computing device. FIG. 9 shows the first computing device 706displaying the first video stream 708 and the second video stream 808,at the same time on the display 706 (e.g., via a split screen format).This is just one example of how the first, video steam and second videostream may be displayed, other methods of displaying the first videostream and second video stream may be used in example embodiments.

In one example, the computing device provides user controls in thedisplay that allow a user to adjust the way the two videos aredisplayed. For example, the display may include a slider between the twovideos that allows a user to adjust the size of the videos so that oneis smaller than the other (e.g., one vide taking up a third of thedisplay and one video taking up two-thirds of the display, etc.), sothat the two videos are equal size in the screen, and so forth. In oneexample, the computing device automatically adjusts the display based onthe orientation of the computing device. For example, if the computingdevice is in a vertical orientation the videos may appear one on top ofeach other (e.g., as shown in FIG. 9) and if the computing device is ina horizontal orientation, the videos may appear side by side.

In one example, the first computing device captures both videos as theyare being displayed on the computing device. Alternatively, the videosmay be captured on a backend server. In another example, the videos maybe displayed in a lower quality locally on the computing device (e.g.,depending upon the computing device computing resources and abilities)to conserve resources but then also be captured in a higher qualityformat on the backend server. In this way if the user wants to view thetwo videos later on a device with better computing resources, the videoscan be provided in higher quality. The video stream captured maycomprise metadata with additional information such as instructions tocombine a first video with a second video, a user identifier associatedwith the video, a media item identifier for the video, a computingdevice identifier that captured the video, a time stamp for capture ofthe video, and so forth.

In one example, each video can be controlled separately. For example, afirst video can be paused or stopped while the second video continuesrecording.

Example embodiments may further provide for a user to send a messagecomprising the at least a portion of the first video stream and at leasta portion of the second video stream, to one or more other users. Forexample, the first computing device receives an indication (e.g.,request) from the first user to send a message with a portion of thefirst video stream and at least a portion of the second video stream toa third device associated with a third user. The first user may want toadd text, a media overlay, or other augmentation to the message, asdescribed above. The first computing device generates a messagecomprising the at least one portion of the first video stream and the atleast one portion of the second video stream (and any added text, mediaoverlay, etc.). FIG. 10 shows an example message comprising the at leastone portion of the first video stream and the at least one portion ofthe second video stream and text input by the first user. The firstcomputing device sends the generated message to the third computingdevice. The third computing device receives the generated message via athird computing device and displays the two video streams on the thirdcomputing device. The two video streams may be displayed in a splitscreen or other format, as explained above. In one example, the messageis an ephemeral message that is accessible for a time-limited duration,as explained above.

In one example, each video in the message can be controlled separately,as described above. For example, a first video can be paused or stoppedwhile the second video continues recording.

Example embodiments may further provide for a user to add the at leastone portion of the first video stream and at least one portion of thesecond video stream, to a media collection. For example, the firstcomputing device may receive an indication (e.g., request) from thefirst user to add at least one portion of the first video stream and atleast one portion of the second video stream to a media collection. Inone example, the first computing device may then add the at least oneportion of the first video and the at least one portion of the videostream to the media collection.

In one example, the first user may want to add text, a media overlay, orother augmentation to the message, as described above. The firstcomputing device generates a message or media content item comprisingthe at least one portion of the first video stream and the at least oneportion of the second video stream (and optionally any added text, mediaoverlay, etc.). FIG. 10 shows an example message comprising the at leastone portion of the first video stream and the at least one portion ofthe second video stream and text input by the first user. The firstcomputing device may add the generated message to the media collection.One or more other users may access the media collection to view themessage. For example, a third user may view the generated message via athird computing device and view the two video streams on the thirdcomputing device.

In one example, the third computing device adds the at least one portionof the first video stream and at least one portion of the second videostream to a media collection by sending the at least one portion of thefirst video stream and at least one portion of the second video streamto a server system (e.g., server system 108) to be added to the mediacollection. In another example, the third computing device adds themessage or media content item comprising the at least one portion of thefirst video stream and at least one portion of the second video stream(and any text, media overlay, etc.) to a media collection by sending themessage or media content item to a server computer to be added to themedia collection. In another example the message or media content itemis generated by the server computer and then added by the servercomputer to the media collection.

Example embodiments describe many operations and functionality performedby a computing device, such as a client device 102. The describedoperations and functionality may also be performed by one or more servercomputers (e.g., the multi-video capture system 124 in server system108). In other examples, the operations and functionality may beperformed by a combination of one or more client devices 102 and serversystem 108.

FIG. 11 is a block diagram 1100 illustrating software architecture 1102,which can be installed on any one or more of the devices describedabove. For example, in various embodiments, client devices 102 andserver systems 108, including server systems 110, 112, 114, 116, 118,122, and 124 may be implemented using some or all of the elements ofsoftware architecture 1102. FIG. 11 is merely a non-limiting example ofa software architecture, and it will be appreciated that many otherarchitectures can be implemented to facilitate the functionalitydescribed herein. In various embodiments, the software architecture 1102is implemented by hardware such as machine 1200 of FIG. 12 that includesprocessors 1210, memory 1230, and I/O components 1250. In this example,the software architecture 1102 can be conceptualized as a stack oflayers where each layer may provide a particular functionality. Forexample, the software architecture 1102 includes layers such as anoperating system 1104, libraries 1106, frameworks 1108, and applications1110. Operationally, the applications 1110 invoke applicationprogramming interface (API) calls 1112 through the software stack andreceive messages 1114 in response to the API calls 1112, consistent withsome embodiments.

In various implementations, the operating system 1104 manages hardwareresources and provides common services. The operating system 1104includes, for example, a kernel 1120, services 1122, and drivers 1124.The kernel 1120 acts as an abstraction layer between the hardware andthe other software layers, consistent with some embodiments. Forexample, the kernel 1120 provides memory management, processormanagement (e.g., scheduling), component management, networking, andsecurity settings, among other functionality. The services 1122 canprovide other common services for the other software layers. The drivers1124 are responsible for controlling or interfacing with the underlyinghardware, according to some embodiments. For instance, the drivers 1124can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH®Low Energy drivers, flash memory drivers, serial communication drivers(e.g., Universal Serial Bus (USB) drivers), WI-FI® drivers, audiodrivers, power management drivers, and so forth.

In some embodiments, the libraries 1106 provide a low-level commoninfrastructure utilized by the applications 1110. The libraries 1106 caninclude system libraries 1130 (e.g., C standard library) that canprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 1106 can include API libraries 1132 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media formats such as Moving Picture Experts Group-4 (MPEG4),Advanced Video Coding (H.264 or AVC), Moving Picture Experts GroupLayer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR)audio codec, Joint Photographic Experts Group (JPEG or JPG), or PortableNetwork Graphics (PNG)), graphics libraries (e.g., an OpenGL frameworkused to render in two dimensions (2D) and three dimensions (3D) ingraphic content on a display), database libraries (e.g., SQLite toprovide various relational database functions), web libraries (e.g.,WebKit to provide web browsing functionality), and the like. Thelibraries 1106 can also include a wide variety of other libraries 1134to provide many other APIs to the applications 1110.

The frameworks 1108 provide a high-level common infrastructure that canbe utilized by the applications 1110, according to some embodiments. Forexample, the frameworks 1108 provide various graphic user interface(GUI) functions, high-level resource management, high-level locationservices, and so forth. The frameworks 1108 can provide a broad spectrumof other APIs that can be utilized by the applications 1110, some ofwhich may be specific to a particular operating system 1104 or platform.

In an example embodiment, the applications 1110 include a homeapplication 1150, a contacts application 1152, a browser application1154, a book reader application 1156, a location application 1158, amedia application 1160, a messaging application 1162, a game application1164, and a broad assortment of other applications such as a third partyapplications 1166 and media content application 1167. According to someembodiments, the applications 1110 are programs that execute functionsdefined in the programs. Various programming languages can be employedto create one or more of the applications 1110, structured in a varietyof manners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, the third partyapplication 1166 (e.g., an application developed using the ANDROID™ orIOS™ software development kit (SDK) by an entity other than the vendorof the particular platform) may be mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating system. In this example, the third party application1166 can invoke the API calls 1112 provided by the operating system 1104to facilitate functionality described herein.

As explained above, some embodiments may particularly include amessaging application 1162. In certain embodiments, this may be astand-alone application that operates to manage communications with aserver system such as server system 108. In other embodiments, thisfunctionality may be integrated with another application such as a mediacontent viewing application 1167. Messaging application 1162 may requestand display various media content items and may provide the capabilityfor a user to input data related to media content items via a touchinterface, keyboard, or using a camera device of machine 1200,communication with a server system 108 via I/O components 1250, andreceipt and storage of media content items in memory 1230. Presentationof media content items and user inputs associated with media contentitems may be managed by messaging application 1162 using differentframeworks 1108, library 1106 elements, or operating system 1104elements operating on a machine 1200.

FIG. 12 is a block diagram illustrating components of a machine 1200,according to some embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 12 shows a diagrammatic representation of the machine1200 in the example form of a computer system, within which instructions1216 (e.g., software, a program, an application 1110, an apples, an app,or other executable code) for causing the machine 1200 to perform anyone or more of the methodologies discussed herein can be executed. Inalternative embodiments, the machine 1200 operates as a standalonedevice or can be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 1200 may operate in the capacity of aserver system 108, 110, 112, 114, 116, 118, 122, 124, etc. or a clientdevice 102 in a server-client network environment, or as a peer machinein a peer-to-peer (or distributed) network environment. The machine 1200can comprise, but not be limited to, a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a personal digital assistant (PDA), anentertainment media system, a cellular telephone, a smart phone, amobile device, a wearable device (e.g., a smart watch), a smart homedevice (e.g., a smart appliance), other smart devices, a web appliance,a network router, a network switch, a network bridge, or any machinecapable of executing the instructions 1216, sequentially or otherwise,that specify actions to be taken by the machine 1200. Further, whileonly a single machine 1200 is illustrated, the term “machine” shall alsobe taken to include a collection of machines 1200 that individually orjointly execute the instructions 1216 to perform any one or more of themethodologies discussed herein.

In various embodiments, the machine 1200 comprises processors 1210,memory 1230, and I/O components 1250, which can be configured tocommunicate with each other via a bus 1202. In an example embodiment,the processors 1210 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a radio-frequency integrated circuit (RFIC), another processor,or any suitable combination thereof) include, for example, a processor1212 and a processor 1214 that may execute the instructions 1216. Theterm “processor” is intended to include multi-core processors 1210 thatmay comprise two or more independent processors 1212, 1214 (alsoreferred to as “cores”) that can execute instructions 1216contemporaneously. Although FIG. 12 shows multiple processors 1210, themachine 1200 may include a single processor 1210 with a single core, asingle processor 1210 with multiple cores (e.g., a multi-core processor1210), multiple processors 1212, 1214 with a single core, multipleprocessors 1210, 1212 with multiples cores, or any combination thereof.

The memory 1230 comprises a main memory 1232, a static memory 1234, anda storage unit 1236 accessible to the processors 1210 via the bus 1202,according to some embodiments. The storage unit 1236 can include amachine-readable medium 1238 on which are stored the instructions 1216embodying any one or more of the methodologies or functions describedherein. The instructions 1216 can also reside, completely or at leastpartially, within the main memory 1232, within the static memory 1234,within at least one of the processors 1210 (e.g., within the processor'scache memory), or any suitable combination thereof, during executionthereof by the machine 1200. Accordingly, in various embodiments, themain memory 1232, the static memory 1234, and the processors 1210 areconsidered machine-readable media 1238.

As used herein, the term “memory” refers to a machine-readable medium1238 able to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 1238 is shown, in an example embodiment, to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 1216. The term “machine-readable medium” shall also betaken to include any medium, or combination of multiple media, that iscapable of storing instructions (e.g., instructions 1216) for executionby a machine (e.g., machine 1200), such that the instructions 1216, whenexecuted by one or more processors of the machine 1200 (e.g., processors1210), cause the machine 1200 to perform any one or more of themethodologies described herein. Accordingly, a “machine-readable medium”refers to a single storage apparatus or device, as well as “cloud-based”storage systems or storage networks that include multiple storageapparatus or devices. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, one or more datarepositories in the form of a solid-state memory (e.g., flash memory),an optical medium, a magnetic medium, other non-volatile memory (e.g.,erasable programmable read-only memory (EPROM)), or any suitablecombination thereof. The term “machine-readable medium” specificallyexcludes non-statutory signals per se.

The I/O components 1250 include a wide variety of components to receiveinput, provide output, produce output, transmit information, exchangeinformation, capture measurements, and so on. In general, it will beappreciated that the I/O components 1250 can include many othercomponents that are not shown in FIG. 12. The I/O components 1250 aregrouped according to functionality merely for simplifying the followingdiscussion, and the grouping is in no way limiting. In various exampleembodiments, the I/O components 1250 include output components 1252 andinput components 1254. The output components 1252 include visualcomponents (e.g., a display such as a plasma display panel (PDP), alight emitting diode (LED) display, a liquid crystal display (LCD), aprojector, or a cathode ray tube (CRT)), acoustic components (e.g.,speakers), haptic components (e.g., a vibratory motor), other signalgenerators, and so forth. The input components 1254 include alphanumericinput components (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and force of touches or touch gestures, orother tactile input components), audio input components (e.g., amicrophone), and the like.

In some further example embodiments, the I/O components 1250 includebiometric components 1256, motion components 1258, environmentalcomponents 1260, or position components 1262, among a wide array ofother components. For example, the biometric components 1256 includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1258 includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1260 include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensor components(e.g., machine olfaction detection sensors, gas detection sensors todetect concentrations of hazardous gases for safety or to measurepollutants in the atmosphere), or other components that may provideindications, measurements, or signals corresponding to a surroundingphysical environment. The position components 1262 include locationsensor components (e.g., a Global Positioning System (GPS) receivercomponent), altitude sensor components (e.g., altimeters or barometersthat detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication can be implemented using a wide variety of technologies.The I/O components 1250 may include communication components 1264operable to couple the machine 1200 to a network 1280 or devices 1270via a coupling 1282 and a coupling 1272, respectively. For example, thecommunication components 1264 include a network interface component oranother suitable device to interface with the network 1280. In furtherexamples, communication components 1264 include wired communicationcomponents, wireless communication components, cellular communicationcomponents, near field communication (NFC) components, BLUETOOTH®components (e.g., BLUETOOTH® Low Energy), WI-FI® components, and othercommunication components to provide communication via other modalities.The devices 1270 may be another machine 1200 or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, in some embodiments, the communication components 1264 detectidentifiers or include components operable to detect identifiers. Forexample, the communication components 1264 include radio frequencyidentification (RFID) tag reader components, NFC smart tag detectioncomponents, optical reader components (e.g., an optical sensor to detecta one-dimensional bar codes such as a Universal Product Code (UPC) barcode, multi-dimensional bar codes such as a Quick Response (QR) code,Aztec Code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code,Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes,and other optical codes), acoustic detection components (e.g.,microphones to identify tagged audio signals), or any suitablecombination thereof. In addition, a variety of information can bederived via the communication components 1264, such as location viaInternet Protocol (IP) geo-location, location via WI-FI® signaltriangulation, location via detecting a BLUETOOTH® or NFC beacon signalthat may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 1280can be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the publicswitched telephone network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a WI-FI®network, another type of network, or a combination of two or more suchnetworks. For example, the network 1280 or a portion of the network 1280may include a wireless or cellular network, and the coupling 1282 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or another type of cellular orwireless coupling. In this example, the coupling 1282 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard-setting organizations, other long rangeprotocols, or other data transfer technology.

In example embodiments, the instructions 1216 are transmitted orreceived over the network 1280 using a transmission medium via a networkinterface device (e.g., a network interface component included in thecommunication components 1264) and utilizing any one of a number ofwell-known transfer protocols (e.g., Hypertext Transfer Protocol(HTTP)). Similarly, in other example embodiments, the instructions 1216are transmitted or received using a transmission medium via the coupling1272 (e.g., a peer-to-peer coupling) to the devices 1270. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying the instructions 1216for execution by the machine 1200, and includes digital or analogcommunications signals or other intangible media to facilitatecommunication of such software.

Furthermore, the machine-readable medium 1238 is non-transitory (inother words, not having any transitory signals) in that it does notembody a propagating signal. However, labeling the machine-readablemedium 1238 “non-transitory” should not be construed to mean that themedium is incapable of movement; the medium 1238 should be considered asbeing transportable from one physical location to another. Additionally,since the machine-readable medium 1238 is tangible, the medium 1238 maybe considered to be a machine-readable device.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: determining a secondcomputing device, of a plurality of computing devices, that is within apredetermined distance from a location of a first computing device;causing display, by the first computing device, of a graphicalindication that a second user associated with the second computingdevice is nearby while displaying a first video stream being captured bythe first computing device; detecting, by the first computing device, aselection of the graphical indication that the second user is nearby,and in response to the selection of the graphical indication that thesecond user is nearby, causing display of further information about thesecond user, an option to send a message to the second user, and anoption to view and capture a second video steam being captured on thesecond computing device; in response to detecting selection of theoption to view the second video stream being captured on the secondcomputing device, displaying the second video stream being captured onthe second computing device on a display of the first computing devicein conjunction with display of the first video stream being captured bythe first computing device; capturing, by the first computing device,the displayed second video stream while continuing to capture the firstvideo stream; generating a message comprising the first video stream andthe second video stream; and sending the generated message comprisingthe first video stream and the second video stream to a third computingdevice.
 2. The method of claim 1, wherein the first video stream and thesecond video stream are displayed at a same time in a split screenformat.
 3. The method of claim 1, wherein the generated message isdisplayed on the third device in a split screen format wherein the firstvideo stream comprises a first part of the split screen and the secondvideo stream comprises a second part of the split screen.
 4. The methodof claim 1, further comprising: receiving a request to add at least oneportion of the first video stream and at least one portion of the secondvideo stream to a media collection; and adding the at least one portionof the first video stream and the at least one portion of the secondvideo stream to the media collection.
 5. The method of claim 1, furthercomprising: receiving a request to add the generated message to a mediacollection; and adding the generated message to the media collection. 6.The method of claim 1, wherein the display of the second video beingcaptured on the second computing device in conjunction with display ofthe first video being captured by the first computing device, furthercomprises a user interface mechanism that allows for adjustment of asize of each of the first video and the second video for display on thefirst computing device.
 7. The method of claim 1, further comprising:detecting an orientation of the first computing device; andautomatically adjusting the display of the second video being capturedon the second computing device in conjunction with display of the firstvideo being captured by the first computing device based on the detectedorientation of the first computing device.
 8. The method of claim 1,wherein capture of the first video and the second video is performedusing a higher quality format and display of the first video and thesecond video is performed using a lower quality format.
 9. The method ofclaim 1, wherein the graphical indication is an icon indicating arelationship of the second user to a first user corresponding to thefirst computing device.
 10. The method of claim 1, further comprising:receiving input of a media overlay to augment the message comprising thefirst video stream and the second video stream; and wherein generatingthe message comprises generating the message comprising the first videostream, the second video stream, input text, and the input mediaoverlay.
 11. A computing device comprising: a processor; and a computerreadable medium coupled with the processor, the computer readable mediumcomprising instructions stored thereon that are executable by theprocessor to cause the computing device to perform operationscomprising: determining a second computing device, of a plurality ofcomputing devices, that is within a predetermined distance from alocation of the computing device, wherein the computing device is afirst computing device; causing display of a graphical indication that asecond user associated with the second computing device is nearby whiledisplaying a first video stream being captured by the first computingdevice; detecting a selection of the graphical indication that thesecond user is nearby, and in response to the selection of the graphicalindication that the second user is nearby, causing display of furtherinformation about the second user, an option to send a message to thesecond user, and an option to view and capture a second video steambeing captured on the second computing device; in response to detectingselection of the option to view the second video stream being capturedon the second computing device, displaying the second video stream beingcaptured on the second computing device on a display of the firstcomputing device in conjunction with display of the first video streambeing captured by the first computing device; capturing the displayedsecond video stream while continuing to capture the first video stream;generating a message comprising the first video stream and the secondvideo stream; and sending the generated message comprising the firstvideo stream and the second video stream to a third computing device.12. The computing device of claim 11, wherein the first video stream andthe second video stream are displayed at a same time in a split screenformat.
 13. The computing device of claim 11, the operations furthercomprising: receiving a request to add at least one portion of the firstvideo stream and at least one portion of the second video stream to amedia collection; and adding the at least one portion of the first videostream and the at least one portion of the second video stream to themedia collection.
 14. The computing device of claim 11, the operationsfurther comprising: receiving a request to add the generated message toa media collection; and adding the generated message to the mediacollection.
 15. The computing device of claim 11, wherein the display ofthe second video being captured on the second computing device inconjunction with display of the first video being captured by the firstcomputing device, further comprises a user interface mechanism thatallows for adjustment of a size of each of the first video and thesecond video for display on the first computing device.
 16. Thecomputing device of claim 11, the operations further comprising:detecting an orientation of the first computing device; andautomatically adjusting the display of the second video being capturedon the second computing device in conjunction with display of the firstvideo being captured by the first computing device based on the detectedorientation of the first computing device.
 17. The computing device ofclaim 11, wherein capture of the first video and the second video isperformed using a higher quality format and display of the first videoand the second video is performed using a lower quality format.
 18. Thecomputing device of claim 11, wherein the graphical indication is anicon indicating a relationship of the second user to a first usercorresponding to the first computing device.
 19. The computing device ofclaim 11, the operations further comprising: receiving input of a mediaoverlay to augment the message comprising the first video stream and thesecond video stream; and wherein generating the message comprisesgenerating the message comprising the first video stream, the secondvideo stream, input text, and the input media overlay.
 20. Anon-transitory computer readable medium comprising instructions storedthereon that are executable by at least one processor to cause a firstcomputing device to perform operations comprising: determining a secondcomputing device, of a plurality of computing devices, that is within apredetermined distance from a location of the first computing device;causing display of a graphical indication that a second user associatedwith the second computing device is nearby while displaying a firstvideo stream being captured by the first computing device; detecting aselection of the graphical indication that the second user is nearby,and in response to the selection of the graphical indication that thesecond user is nearby, causing display of further information about thesecond user, an option to send a message to the second user, and anoption to view and capture a second video steam being captured on thesecond computing device; in response to detecting selection of theoption to view the second video stream being captured on the secondcomputing device, displaying the second video stream being captured onthe second computing device on a display of the first computing devicein conjunction with display of the first video stream being captured bythe first computing device; capturing the displayed second video streamwhile continuing to capture the first video stream; generating a messagecomprising the first video stream and the second video stream; andsending the generated message comprising the first video stream and thesecond video stream to a third computing device.